Last modified: 2014-09-16 08:03:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72369, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70369 - "Failed to archive artifacts" and "java.util.concurrent.ExecutionException"
"Failed to archive artifacts" and "java.util.concurrent.ExecutionException"
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-03 23:36 UTC by Matthew Flaschen
Modified: 2014-09-16 08:03 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Console output for https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/287/console (5.58 KB, text/plain)
2014-09-16 07:57 UTC, Antoine "hashar" Musso (WMF)
Details

Description Matthew Flaschen 2014-09-03 23:36:56 UTC
https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/287/consoleFull has several apparent internal errors:

20:44:14 rm: cannot remove `log': Directory not empty
20:44:14 Build step 'Execute shell' marked build as failure

---

ERROR: Failed to archive artifacts: log/*

---
The second one then goes into various Java errors, which I guess are from the archiver.  And finally:

---
20:44:14 rm: cannot remove `/srv/localhost/qunit/jenkins-mwext-GettingStarted-qunit-287': No such file or directory
Comment 1 Antoine "hashar" Musso (WMF) 2014-09-16 07:57:55 UTC
Created attachment 16481 [details]
Console output for https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/287/console
Comment 2 Antoine "hashar" Musso (WMF) 2014-09-16 08:03:25 UTC
I am not sure what happened.  /log/ is where we have commands log to and it is deleted early on with:

 rm -fr

Maybe a file / inode went corrupted and not properly deleted.  The java code attempted to archive log/mw-debug-www.log which indicates it hasn't been deleted by the rm command.  The stacktrace hints at a corrupted file imho.

Following builds passed though so I guess it was a transient / one time issue. Feel free to reopen if it occurs again.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links