[llvm-dev] bugzilla complaining about "unexpected error"

Tue Oct 5 01:44:21 PDT 2021

I haven't seen any email notifications related to your updates to PR51946 today. That is quite annoying.

/Björn

> -----Original Message-----
> From: Mikael Holmén <mikael.holmen at ericsson.com>
> Sent: den 5 oktober 2021 10:29
> To: Björn Pettersson A <bjorn.a.pettersson at ericsson.com>; llvm-
> admin at lists.llvm.org; Mikael Holmén <mikael.holmen at ericsson.com>
> Cc: llvm-dev <llvm-dev at lists.llvm.org>
> Subject: Re: bugzilla complaining about "unexpected error"
> 
> And to add, when I tried attaching an ll-file to the same PR I got:
> 
> Internal Server Error
> 
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
> 
> Please contact the server administrator at llvm-admin at lists.llvm.org to
> inform them of the time this error occurred, and the actions you performed
> just before this error.
> 
> More information about this error may be available in the server error log.
> 
> 
> Also in this case, the file did indeed get attached, but no idea if any on
> the CC list got notified.
> 
> /Mikael
> 
> ________________________________________
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Mikael Holmén
> via llvm-dev <llvm-dev at lists.llvm.org>
> Sent: Tuesday, October 5, 2021 10:24 AM
> To: Björn Pettersson A; llvm-admin at lists.llvm.org
> Cc: llvm-dev
> Subject: Re: [llvm-dev] bugzilla complaining about "unexpected error"
> 
> I got the same error message right now (but for anopther PR than last
> time):
> 
>  An unexpected error occurred. This could be a temporary problem, or some
> code is behaving incorrectly. If this problem persists, please email this
> page to llvm-admin at lists.llvm.org with details of what you were doing at
> the time this message appeared.
> 
> URL: https://protect2.fireeye.com/v1/url?k=48b2fbd9-1729c2d9-48b2bb42-
> 86fc6812c361-b3a5cbe153795eee&q=1&e=f62d29ad-7e0e-401f-9387-
> a5c8a4eb426b&u=https%3A%2F%2Fbugs.llvm.org%2Fprocess_bug.cgi%3Fclassificati
> on%3DUnclassified%26assigned_to%3Dunassignedbugs%2540nondot.org%26comment%3
> DThe%2520same%2520assert%2520can%2520also%2520be%2520seen%2520with%253A%250
> D%250A%2520opt%2520-
> passes%253D%2522cgscc%2528devirt%253C4%253E%2528inline%2529%2529%252Cfuncti
> on%2528slp-
> vectorizer%2529%252Ccgscc%2528devirt%253C4%253E%2528function%2528sroa%2529%
> 2529%2529%2522%2520-o%2520%252Fdev%252Fnull%2520bbi-53898_2.ll%2520-aa-
> pipeline%253Ddefault%250D%250A%250D%250AIn%2520this%2520case%2520it%2520sta
> rts%2520happening%2520with%2520commit%252078d4096d037%253A%250D%250A%2520%2
> 520%2520%2520%255BLazyCallGraph%255D%2520Add%2520invalidate%2520method.%250
> D%250A%2520%2520%2520%2520%250D%250A%2520%2520%2520%2520Summary%253A%2520Ad
> d%2520invalidate%2520method%2520in%2520LazyCallGraph.%250D%250A%2520%2520%2
> 520%2520%250D%250A%2520%2520%2520%2520Reviewers%253A%2520chandlerc%252C%252
> 0silvas%250D%250A%2520%2520%2520%2520%250D%250A%2520%2520%2520%2520Subscrib
> ers%253A%2520hiraditya%252C%2520sanjoy.google%252C%2520llvm-
> commits%250D%250A%2520%2520%2520%2520%250D%250A%2520%2520%2520%2520Tags%253
> A%2520%2523llvm%250D%250A%2520%2520%2520%2520%250D%250A%2520%2520%2520%2520
> Differential%2520Revision%253A%2520https%253A%252F%252Freviews.llvm.org%252
> FD72817%250D%250A%250D%250AIn%2520a%2520later%2520commit%252C%25206699029b6
> 7b%252C%2520-aa-
> pipeline%253Ddefault%2520was%2520made%2520the%2520default%252C%2520so%2520a
> fter%2520that%2520it%2520can%2520be%2520reproduced%2520with%2520just%250D%2
> 50A%2520%2520opt%2520-
> passes%253D%2522cgscc%2528devirt%253C4%253E%2528inline%2529%2529%252Cfuncti
> on%2528slp-
> vectorizer%2529%252Ccgscc%2528devirt%253C4%253E%2528function%2528sroa%2529%
> 2529%2529%2522%2520-o%2520%252Fdev%252Fnull%2520bbi-
> 53898_2.ll%26newalias%3D%26id%3D51946%26bug_status%3DNEW%26remaining_time%3
> D0.0%26component%3DInterprocedural%2520Optimizations%26estimated_time%3D0.0
> %26rep_platform%3DPC%26bug_severity%3Denhancement%26dependson%3D%26op_sys%3
> DLinux%26version%3Dtrunk%26delta_ts%3D2021-09-
> 23%252005%253A35%253A25%26priority%3DP%26work_time%3D0%26blocked%3D%26short
> _desc%3Dopt%2520-passes%253D%2527cgscc%2528require%253Cfam-
> proxy%253E%2529%252Cipsccp%252Cscc-oz-module-
> inliner%2527%2520fails%2520with%2520Assertion%2520%2560%2528E%2520%257C%257
> C%2520%2521FunctionPass%2529%26product%3Dlibraries%26deadline%3D%26bug_file
> _loc%3D%26token%3D1633421733-dXmIzxuysImXJAUDZgfe7YM2FqAEtboFOSu-
> 4lNkkdQ%26tag%3D%26see_also%3D%26cf_fixed_by_commits%3D%26defined_bug_ignor
> ed%3D1%26dup_id%3D%26keywords%3D%26resolution%3D
> undef error - This shouldn't happen at /usr/share/perl/5.18/Text/Wrap.pm
> line 84.
> 
> Traceback:
> 
> 
> I got it when adding a comment, and the comment did get added even with the
> above error, but I don't know if mail notifications were sent out of people
> on the issue CC list or not.
> 
> /Mikael
> 
> ________________________________________
> From: Björn Pettersson A <bjorn.a.pettersson at ericsson.com>
> Sent: Tuesday, September 28, 2021 1:51 PM
> To: llvm-admin at lists.llvm.org
> Cc: Mikael Holmén; llvm-dev
> Subject: bugzilla complaining about "unexpected error"
> 
> Hi!
> 
> Recently I've seen errors like this in Bugzilla when I've added comments
> etc to trouble reports:
> 
> 
> An unexpected error occurred. This could be a temporary problem, or some
> code is behaving incorrectly. If this problem persists, please email this
> page to llvm-admin at lists.llvm.org with details of what you were doing at
> the time this message appeared.
> 
> URL: https://protect2.fireeye.com/v1/url?k=841c798f-db87408f-841c3914-
> 86fc6812c361-6c66dbf466ab0695&q=1&e=f62d29ad-7e0e-401f-9387-
> a5c8a4eb426b&u=https%3A%2F%2Fbugs.llvm.org%2Fprocess_bug.cgi%3Frep_platform
> %3DPC%26product%3Dlibraries%26bug_status%3DNEW%26classification%3DUnclassif
> ied%26delta_ts%3D2021-09-
> 27%252007%253A17%253A58%26deadline%3D%26defined_bug_ignored%3D1%26keywords%
> 3D%26token%3D1632826824-
> LaTofBNN2ThrLhV2WPxFfYGudi4QLRucdsbG96dubu0%26blocked%3D%26bug_severity%3De
> nhancement%26resolution%3D%26component%3DLoop%2520Optimizer%26priority%3DP%
> 26cf_fixed_by_commits%3D%26estimated_time%3D0.0%26dup_id%3D%26assigned_to%3
> Dunassignedbugs%2540nondot.org%26bug_file_loc%3D%26short_desc%3Dopt%2520-
> passes%253D%2527loop-mssa%2528canon-freeze%252Cloop-
> rotate%2529%252Cfunction%2528bounds-
> checking%2529%2527%2520fails%2520with%2520Assertion%2520%2560isAvailableAtL
> oopEntry%2528OrigStartMinusStride%252C%2520L%2529%2520%2526%2526%2520%2522M
> ust%2520be%2521%2522%2527%26version%3Dtrunk%26op_sys%3DLinux%26dependson%3D
> %26newalias%3D%26addselfcc%3Don%26comment%3DJust%2520some%2520additional%25
> 20info.%250D%250A%250D%250AIt%2520also%2520fails%2520when%2520using%2520dif
> ferent%2520loop%2520pass%2520managers%2520like%2520this%253A%250D%250A%250D
> %250A%2520%2520-passes%253D%2527loop-mssa%2528canon-freeze%2529%252Cloop-
> mssa%2528loop-rotate%2529%252Cfunction%2528bounds-
> checking%2529%2527%250D%250A%250D%250A%250D%250AIf%2520we%2520invalidate%25
> 20scalar-evolution%2520after%2520canon-
> freeze%2520like%2520this%250D%250A%250D%250A%2520%2520-
> passes%253D%2527loop-mssa%2528canon-freeze%2529%252Cinvalidate%253Cscalar-
> evolution%253E%252Cloop-mssa%2528loop-rotate%2529%252Cfunction%2528bounds-
> checking%2529%2527%250D%250A%250D%250Athen%2520it%2520works%2520fine%2520%2
> 528and%2520also%2520if%2520we%2520split%2520this%2520into%2520running%2520o
> pt%2520twice%2520with%2520canon-
> freeze%2520in%2520the%2520first%2520run%2520and%2520the%2520rest%2520of%252
> 0the%2520pipeline%2520in%2520a%2520subsequent%2520run%2529.%2520So%2520mayb
> e%2520it%2520is%2520canon-
> freeze%2520that%2520isn%2527t%2520updating%2520scalar-
> evolution%2520analysis%2520correctly.%26id%3D51981%26tag%3D%26work_time%3D0
> %26see_also%3D%26remaining_time%3D0.0
> undef error - This shouldn't happen at /usr/share/perl/5.18/Text/Wrap.pm
> line 84.
> 
> 
> 
> 
> Those are a bit annoying, but the tickets at least seem to get updated
> anyway.
> Although, there are some suspicion that some email-notifications might go
> missing (at least one time it has happened that the reporter of a bug did
> not receive an email when I added comments to a PR).
> 
> 
> This time it was related to PR51981, and I simply got the failure message
> above when adding "Comment 1".
> 
> According to Mikael (who wrote the ticket):
> - he got a similar message when writing the ticket
> - he did not receive any email notification when I wrote my comment
> - he got a similar message when adding himself as CC, and when doing that
> he also got an error message like above
> 
> 
> Regards,
> Björn
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://protect2.fireeye.com/v1/url?k=8ee1ded7-d17ae7d7-8ee19e4c-
> 86fc6812c361-68b83affca05402e&q=1&e=f62d29ad-7e0e-401f-9387-
> a5c8a4eb426b&u=https%3A%2F%2Flists.llvm.org%2Fcgi-
> bin%2Fmailman%2Flistinfo%2Fllvm-dev