Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#950 Updated How Rultor Works #991

Closed
wants to merge 40 commits into from
Closed

#950 Updated How Rultor Works #991

wants to merge 40 commits into from

Conversation

gumbelmj
Copy link
Contributor

Updated the Readme. Some checks failed. Do I need to be concerned about these?

@alex-palevsky
Copy link
Contributor

@gumbelmj Thanks for your pull request, let me find someone who can review it

@alex-palevsky
Copy link
Contributor

@caarlos0 review this please

<li>Reports back to you, in the GitHub pull request.</li>
</ol>
You can see it in action, for example, in this pull request:
<a href="https://github.com/jcabi/jcabi-github/pull/878">jcabi/jcabi-github#878</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gumbelmj this is a markdown file, please, use markdown syntax.

@caarlos0
Copy link
Contributor

@gumbelmj no need to be concerned about the failed checks, I already opened issues for them: #993 and #722

@caarlos0
Copy link
Contributor

@gumbelmj please see my comment above

@gumbelmj
Copy link
Contributor Author

I updated the pull request, but even MORE tests failed? Is that my issue? And if so, what's wrong?

@caarlos0
Copy link
Contributor

@gumbelmj thanks!

@caarlos0
Copy link
Contributor

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 27, 2016

@rultor merge

@caarlos0 Thanks for your request. @yegor256 Please confirm this.

@caarlos0
Copy link
Contributor

@yegor256 ping

@yegor256
Copy link
Owner

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 29, 2016

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Jan 29, 2016

@rultor merge

@gumbelmj @yegor256 Oops, I failed. You can see the full log here (spent 2min)

+ args=' --ff-only'
+ export BRANCH=__rultor
+ BRANCH=__rultor
++ git show-branch __rultor
++ wc -l
+ '[' 0 -gt 0 ']'
+ git checkout fork/master
Note: checking out 'fork/master'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at c719973... #950 Update How Rultor works from HTML to Markdown
+ git checkout -b __rultor
Switched to a new branch '__rultor'
+ git checkout master
Switched to branch 'master'
+ '[' true == true ']'
+ git checkout __rultor
Switched to branch '__rultor'
+ git rebase master
First, rewinding head to replay your work on top of it...
Applying: 950 Updated How Rultor Works
Applying: #950 Update How Rultor works from HTML to Markdown
+ git checkout master
Switched to branch 'master'
+ '[' false == true ']'
+ git merge --ff-only __rultor
Updating 51fb2df..7a4786f
Fast-forward
 README.md | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)
+ docker_when_possible
+ true
++ uptime
++ sed 's/ /\n/g'
++ tail -n 1
+ load=0.02
++ echo 0.02 '>' 30
++ bc
+ '[' 0 -eq 1 ']'
+ echo 'load average is 0.02, low enough to run a new Docker container'
load average is 0.02, low enough to run a new Docker container
+ break
+ cd ..
+ '[' -n '' ']'
+ use_image=yegor256/rultor
+ docker pull yegor256/rultor
Using default tag: latest
Post http:///var/run/docker.sock/v1.20/images/create?fromImage=yegor256%2Frultor%3Alatest: dial unix /var/run/docker.sock: no such file or directory.
* Are you trying to connect to a TLS-enabled daemon without TLS?
* Is your docker daemon up and running?
'cid' file is absent, container wasn't started correctly

@yegor256
Copy link
Owner

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 29, 2016

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Jan 29, 2016

@rultor merge

@gumbelmj @yegor256 Oops, I failed. You can see the full log here (spent 15min)

    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
    from /var/lib/gems/2.2.0/gems/safe_yaml-1.0.4/lib/safe_yaml/load.rb:131:in `<module:SafeYAML>'
    from /var/lib/gems/2.2.0/gems/safe_yaml-1.0.4/lib/safe_yaml/load.rb:26:in `<top (required)>'
    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
    from /var/lib/gems/2.2.0/gems/jekyll-3.1.0/lib/jekyll.rb:28:in `<top (required)>'
    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
    from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
    from /var/lib/gems/2.2.0/gems/jekyll-3.1.0/bin/jekyll:6:in `<top (required)>'
    from /usr/local/bin/jekyll:23:in `load'
    from /usr/local/bin/jekyll:23:in `<main>'
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.247 s
[INFO] Finished at: 2016-01-29T01:39:27+00:00
[INFO] Final Memory: 16M/276M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (jekyll-build) on project rultor: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (jekyll-build) on project rultor: Command execution failed.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.
    at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:276)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    ... 19 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:660)
    at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:265)
    ... 21 more
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
container 13b21f61902081ccf00b2c1bc60fe67350d8d2d80f9a2a9164616bea13f47c63 is dead
Fri Jan 29 01:40:02 UTC 2016

@@ -26,15 +26,27 @@ TBD... _product statement_

## What Problem Does Rultor Solve?

TBD... _stakeholders and needs_
TBD... _stakeholders and need
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gumbelmj you are missing the closing _ at the end of the line here...

@gumbelmj
Copy link
Contributor Author

@caarlos0 Doh! I missed that it even changed. Thanks. I fixed it.

@caarlos0
Copy link
Contributor

@yegor256 can we try again?

@yegor256
Copy link
Owner

@rultor try to merge

@rultor
Copy link
Collaborator

rultor commented Feb 12, 2016

@rultor try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Feb 12, 2016

@rultor try to merge

@yegor256 Done! FYI, the full log is here (took me 12min)

Bernardo and others added 7 commits February 12, 2016 22:43
@caarlos0
Copy link
Contributor

@yegor256 rultor is strange here... it says it merged the pull, but looks like it didn't

@caarlos0
Copy link
Contributor

@gumbelmj merge conflicts

* Created new ShellCommand class to encapsulated running a command in a shell
* Used ShellCommand to make EndsDaemon use fewer objects and remove duplicate
logic for sanitizing and running commands in EndsDaemon
@gumbelmj
Copy link
Contributor Author

@caarlos0 I believe I fixed the merge conflicts.

@caarlos0
Copy link
Contributor

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Feb 17, 2016

@rultor merge

@caarlos0 Thanks for your request. @yegor256 Please confirm this.

@original-brownbear
Copy link
Contributor

@gumbelmj @caarlos0 even though the team file is not yet updated, but by the power vested in me ...

This should not be merged! The ticket asks for the readme file to be updated, this PR changes 14 files and would break the build anyhow and not pass(messes up the Jekyll gemset).
The merge conflicts were not resolved correctly and from the looks of it this branch is pretty much beyond repair.
Also see #935, your branch is called master, so this bug will prevent a merge either way.
@gumbelmj I would suggest to create a new branch from current master, call it 950 like the issue it is resolving and then simply make your edits to the readme file in one commit and put in a new PR.
This one can be closed I think.

@caarlos0
Copy link
Contributor

@original-brownbear makes sense, seems like a wrong merge...

@gumbelmj
Copy link
Contributor Author

@caarlos0 I'm closing this pull request and I will open a new one to resolve this issue.

@alex-palevsky
Copy link
Contributor

@caarlos0 10 mins added to @original-brownbear account (our architect), payment ID is AP-4JA624692F077145S, since quality is good here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants