Description of problem: Could you update f25 branch's uglify-js.spec to 2.7.0? I saw the rawhide(master) is updated to 2.7.0 yesterday. f25 rubygem-uglifier want to use it. Thanks.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hello, Jared K. Smith I am writing this message here too, though I sent email to you. Could you update below your commit to f25 branch? Because rubygem-uglifier wants to use it. ``` commit 4fbe8e858203b69334e94dcd324795b4bae3ccb5 Author: Jared K. Smith <jaredsmith> Date: Wed Jul 27 21:05:45 2016 -0400 Update to upstream 2.7.0 release ``` Thanks.
I took the owner by myself, because the owner was orphan. And pushed it by myself to f25. Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=15088456 Thanks.
(In reply to Jun Aruga from comment #4) > I took the owner by myself, because the owner was orphan. > And pushed it by myself to f25. > > Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=15088456 > > Thanks. Sorry my mistake. above is scratch build and success. However http://koji.fedoraproject.org/koji/taskinfo?taskID=15088738 is failed.
"fedpkg build" was failed like this. https://kojipkgs.fedoraproject.org//work/tasks/8765/15088765/build.log ``` + /usr/bin/node test/run-tests.js ... 41 passing (37s) 3 failing 1) bin/uglifyjs should produce a functional build when using --self: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test. 2) let Should not produce `let` as a variable name in mangle: Error: timeout of 10000ms exceeded. Ensure the done() callback is being called in this test. at Context.<anonymous> (test/mocha/let.js:27:9) 3) spidermonkey export/import sanity test should produce a functional build when using --self with spidermonkey: Error: timeout of 20000ms exceeded. Ensure the done() callback is being called in this test. ```
The failed one ran on an ARM builder, which will be slower than the x86 builder that the scratch build ran on. You probably just need to increase the timeout in the tests.
(In reply to Tom Hughes from comment #7) > The failed one ran on an ARM builder, which will be slower than the x86 > builder that the scratch build ran on. > > You probably just need to increase the timeout in the tests. I got it. Thank you for your information. The difference of scratch build x86 builder and build ARM builder makes our package development harder. Scratch build: success => push to the branch => build: failure. I may push my modification to the branch many times in this situation.
HI, Tom, Thanks I could build successfully after increasing the timeout in the tests. I pushed it to both f25 and master(rawhide). f25 fedpkg build http://koji.fedoraproject.org/koji/taskinfo?taskID=15089615 http://pkgs.fedoraproject.org/cgit/rpms/uglify-js.git/commit/?h=f25 rawhide fedpkg build http://koji.fedoraproject.org/koji/taskinfo?taskID=15089900 http://pkgs.fedoraproject.org/cgit/rpms/uglify-js.git/commit/