All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/3] CI: Rename travis script directory
Date: Tue, 1 Jun 2021 11:51:29 +0200	[thread overview]
Message-ID: <YLYDITE2xCkzfAOX@pevik> (raw)
In-Reply-To: <YLX7K7oPmSSqXfxO@yuki>

Hi Cyril,

> Hi!
> > I'm sorry, didn't read carefully that the first ack isn't for whole patchset,
> > thus merged whole patchset with your ack.

> The rest looks good as well and we really need working CI so no
> problem...
FYI: there are temporary repository sync problem on Tumbleweed
(problematic obviously both last Travis CI build and new GitHub
Actions builds):

No provider of 'ruby2.5-rubygem-asciidoctor' found.
https://travis-ci.org/github/linux-test-project/ltp/jobs/773129654
https://github.com/linux-test-project/ltp/runs/2717311009

It should be fixed soon.

Kind regards,
Petr

  reply	other threads:[~2021-06-01  9:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 16:50 [LTP] [PATCH 0/3] CI: Move from Travis to GitHub Actions Petr Vorel
2021-05-31 16:50 ` [LTP] [PATCH 1/3] build.sh: Rewrite to allow running certain step Petr Vorel
2021-06-01  9:10   ` Cyril Hrubis
2021-05-31 16:50 ` [LTP] [PATCH 2/3] CI: Rename travis script directory Petr Vorel
2021-06-01  9:11   ` Cyril Hrubis
2021-06-01  9:40     ` Petr Vorel
2021-06-01  9:17       ` Cyril Hrubis
2021-06-01  9:51         ` Petr Vorel [this message]
2021-05-31 16:50 ` [LTP] [PATCH 3/3] CI: Move from Travis to GitHub Actions Petr Vorel
2021-06-01  9:16   ` Cyril Hrubis
2021-06-01  9:50     ` Li Wang
2021-06-01  9:53     ` Petr Vorel
2021-06-01  9:52 ` [LTP] [PATCH 0/3] " Jan Stancek
2021-06-01 10:03   ` Petr Vorel
2021-06-01 14:21   ` Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLYDITE2xCkzfAOX@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.